Wearable device for event access, payment for  offline transactions at the event, and visual light display

ABSTRACT

A wearable device receives ticket information for an event and information indicating a quantity of funds allocated from an account, associated with a user of a user device, to the wearable device, and stores the ticket information and the information indicating the quantity of funds. The wearable device utilizes a wireless component to pair the wearable device and the user device, and provides, to the user device and via the wireless component, the ticket information and information indicating access privileges for the event. The wearable device generates a token for a PoS device for a charge incurred at the event during an offline transaction with the PoS device, and provides, via a NFC component, the token to the PoS device. The wearable device provides, to the user device and via the wireless component, information indicating that that the token was provided to the PoS device.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/157,617, filed Oct. 11, 2018 (now U.S. patent application Ser. No.10,332,100), which is a continuation of U.S. patent application Ser. No.15/922,595, filed Mar. 15, 2018 (now U.S. Pat. No. 10,134,026), whichare incorporated herein by reference.

BACKGROUND

Consumers attend large events, such as a concert, a festival (e.g., amusic festival), an event at a university, a sporting event, an event ata theme park, a trade show, and/or the like. Consumers may not wish tocarry transaction cards (e.g., credit cards, debit cards, and/or thelike) to such events, or such events may not accept transaction cards.

Some organizers of events provide a wearable band that includes ticketinformation and that may be linked to a prepaid transaction card.However, these wearable bands can only perform transactions whenconnected to a network, such as cellular network, a data network, and/orthe like. In addition, these wearable bands do not provide the abilityto check a balance of the prepaid transaction card. Furthermore, thewearable band does not permit the consumer to add funds to the prepaidtransaction card linked to the wearable band. Thus, these wearable bandssolely serve the function of providing ticket information at an event.

SUMMARY

According to some implementations, a wearable device may include anear-field communication (NFC) component, a wireless component, one ormore memories, and one or more processors, communicatively coupled tothe one or more memories, to receive ticket information associated withan event and information indicating a quantity of funds allocated froman account, associated with a user of a user device, to the wearabledevice. The one or more processors may store the ticket information andthe information indicating the quantity of funds in the one or morememories, and may utilize the wireless component to pair the wearabledevice and the user device based on a request to pair that is receivedfrom the user device. The one or more processors may provide, to theuser device and via the wireless component, wearable device information,where the wearable device information includes at least the ticketinformation, and information indicating access privileges associatedwith the event. The one or more processors may generate a token for apoint of sale device for a charge incurred at the event during anoffline transaction with the point of sale device, and may provide, viathe NFC component, the token to the point of sale device, the point ofsale device to utilize the token to receive payment for the charge fromthe account associated with the user, at a later time and via an onlinetransaction. The one or more processors may provide, to the user deviceand via the wireless component, information indicating that that thetoken was provided to the point of sale device, the user device toupdate the account based on the charge.

According to some implementations, a method may include storing, by awearable device, ticket information associated with an event andinformation indicating a quantity of funds allocated from an account,associated with a user of a user device, to the wearable device, wherethe ticket information and the information indicating the quantity offunds being received from one or more devices associated with the event,and the wearable device includes a near-field communication (NFC)component, and a wireless component. The method may include receiving,via the wireless component of the wearable device, a request to pairfrom the user device, and pairing, via the wireless component of thewearable device, the user device and the wearable device based on therequest to pair. The method may include receiving, via the NFC componentof the wearable device, a signal from a point of sale device, where thesignal indicates a charge incurred at the event during an offlinetransaction with the point of sale device, and generating, by thewearable device and based on the signal, a token for the charge incurredat the event during the offline transaction with the point of saledevice. The method may include providing, via the NFC component of thewearable device, the token to the point of sale device, the point ofsale device to utilize the token to receive payment for the charge fromthe account associated with the user, at a later time and via an onlinetransaction, and providing, to the user device and via the wirelesscomponent of the wearable device, information indicating that that thetoken was provided to the point of sale device, the user device toupdate the account based on the charge.

According to some implementations, a non-transitory computer-readablemedium may store instructions that include one or more instructionsthat, when executed by one or more processors of a wearable device thatincludes a near-field communication (NFC) component, a wirelesscomponent, and a security component, cause the one or more processors tostore ticket information associated with an event and informationindicating a quantity of funds allocated from an account, associatedwith a user attending the event, to the wearable device. The one or moreinstructions may cause the one or more processors to receive, via thewireless component, a request to pair the wearable device and a userdevice associated with the user, and pair, via the wireless component,the wearable device and the user device based on the request to pair.The one or more instructions may cause the one or more processors toprovide, to the user device and via the wireless component, theinformation indicating the quantity of funds allocated from the accountto the wearable device, and receive, via the NFC component, a signalfrom a point of sale device, where the signal indicates a chargeincurred at the event, no online communication are provided at the eventfor the wearable device, the user device, and the point of sale device,and the charge is incurred during an offline transaction with the pointof sale device. The one or more instructions may cause the one or moreprocessors to generate, by the security component and based on thesignal, a token for the charge incurred at the event during the offlinetransaction with the point of sale device, and provide, via the NFCcomponent, the token to the point of sale device, the point of saledevice to utilize the token to receive payment for the charge from theaccount associated with the user, at a later time and via an onlinetransaction. The one or more instructions may cause the one or moreprocessors to provide, to the user device and via the wirelesscomponent, information indicating that that the token was provided tothe point of sale device, the user device to update the account based onthe charge.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1I are diagrams of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2; and

FIG. 4 is a flow chart of an example process for utilizing a wearabledevice to access an event, pay for offline transactions at the event,and provide a visual light display.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

Some implementations described herein include a wearable device thatprovides access to an event, pays for offline transactions at the event,and provides a visual light display. The wearable device may include awireless component, a near-field communication (NFC) component, asecurity element, a network receiver component, and multiplelight-emitting diodes (LEDs). The wireless component may enable thewearable device to connect to a user device (e.g., a mobile phone) sothat a user of the wearable device may check a balance of fundsavailable to the wearable device and may add to the balance of funds.The NFC component and the security element may enable the wearabledevice to be used to pay for offline transactions at the event. Thenetwork receiver component and the multiple LEDs may enable the wearabledevice to provide a variety of light displays that may be synchronizedto sounds (e.g., music) associated with the event.

FIGS. 1A-1I are diagrams of an overview of an example implementation 100described herein. As shown in FIG. 1A, a user device may be associatedwith a user and an event platform. The user may utilize the user deviceto purchase a ticket for an event and to add funds to the ticket. Forexample, the user device may provide a user interface that enables theuser to purchase the ticket, add funds to the ticket, provide an account(e.g., xxxx-xxxx) to use for purchasing the ticket and for adding thefunds, provide an amount of funds (e.g., $100) to add to the ticket,and/or the like. In some implementations, the event may include aconcert, a festival (e.g., a music festival), an event at a university,a sporting event, an event at a theme park, a trade show, and/or thelike.

As further shown in FIG. 1A, and by reference number 105, the userdevice may provide, to the event platform, a request for the ticket andthe account to utilize for purchasing the ticket. In someimplementations, the account may include a bank account, a credit cardaccount, a debit card account, and/or the like of the user. As furthershown in FIG. 1A, and by reference number 110, the user device mayprovide, to the event platform, a request to add funds to the ticket.For example, the request to add funds may indicate that the user wishesto add $100 to the ticket and wishes to add the funds to the ticket fromthe account associated with the user.

In some implementations, the event platform may receive the request forthe ticket, the account to utilize for purchasing the ticket, and therequest to add funds to the ticket. The event platform may charge theaccount for the ticket, and may generate a ticket number (e.g., ABC123)based on the request for the ticket and the account to utilize forpurchasing the ticket. The event platform may charge the amount of funds(e.g., $100) to the account, and may add the funds to the ticket. Insome implementations, the ticket may be in the form of a wearabledevice, such as a device affixed to a wristband, a device affixed to alanyard, a device affixed to a backpack, and/or the like. In someimplementations, the wearable device may not include any information(e.g., ticket information, monetary value, and/or the like), and theuser may load information on the wearable device (e.g., via the userdevice).

As further shown in FIG. 1A, and by reference number 115, the eventplatform may acknowledge the transaction by providing an acknowledgementto the user device. In some implementations, the acknowledgement mayindicate that the user has purchased one ticket to the event, and that awearable device with the ticket information and the funds of $100 willbe mailed to the user. The user device may receive the acknowledgment,and may display the acknowledgment to the user.

As shown in FIG. 1B, the user may receive a wearable device and a ticketto the event based on purchasing the ticket. In some implementations,the wearable device may include the ticket information (e.g., the ticketnumber ABC123) and information indicating the funds (e.g., $100)available to the wearable device. In some implementations, the wearabledevice may include a band to be worn around a wrist of the user and ahousing connected to the band. Alternatively, the housing of thewearable device may be connected to a mechanism other than the band,such as a lanyard, a connector for connecting to a backpack or anarticle of clothing, and/or the like. As further shown in FIG. 1B, thehousing may support multiple LEDs, and may house a NFC component,security element, a wireless component (e.g., a Bluetooth component),and a network receiver component, as described elsewhere herein.

As further shown in FIG. 1B, the user may utilize the user device torequest a wearable device application that enables the user device tocommunicate with the wearable device. In some implementations, the usermay be required to provide the ticket number (e.g., ABC123) in orderreceive the wearable device application. As further shown in FIG. 1B,and by reference number 120, the user may utilize the user device toprovide user credentials (e.g., provided by the user device, such as atelephone number associated with the user device), the ticketinformation (e.g., the ticket number), and a request for the wearabledevice application to the event platform. The event platform may receivethe user credentials, the ticket information, and the request for thewearable device application.

As further shown in FIG. 1B, and by reference number 125, the eventplatform may compare the ticket information and the user credentials todetermine whether the request for the wearable device application islegitimate. In some implementations, if the ticket information does notcorrelated with the user credentials, the event platform may not providethe wearable device application to the user device. In someimplementations, and as shown by reference number 130, if the ticketinformation correlates with the user credentials, the event platform mayprovide the wearable device application to the user device. The userdevice may receive the wearable device application, and may install thewearable device application on the user device.

As shown in FIG. 1C, the user device may execute the wearable deviceapplication, and the wearable device application may provide a userinterface that inquires whether the user wants to pair the user devicewith the wearable device. In some implementations, and as shown byreference number 135, if the user wants to pair the user device with thewearable device, the wearable device application may cause the userdevice to provide, to the wearable device, a signal requesting pairingwith the wearable device. In some implementations, the wirelesscomponent of the wearable device may receive the signal requesting thepairing. In some implementations, and as shown by reference number 140,the wearable device may automatically accept the pairing with the userdevice and may provide a signal, indicating that the pairing isaccepted, to the user device. In such implementations, the user deviceand the wearable device may be paired and may communicate with eachother. In some implementations, the wearable device may requireprovision of the ticket information or some other verification beforepairing with the user device.

As further shown in FIG. 1C, and by reference number 145, once thewearable device and the user device are paired, the wearable device mayprovide wearable device information to the user device. The user devicemay receive the wearable device information, and may provide thewearable device information for display to the user. In someimplementations, the wearable device information may include the ticketnumber (e.g., ABC123) associated with the wearable device, an amount offunds allocated to the wearable device, information indicating eventaccess privileges, information enabling the user device to set up thelights (e.g., the LEDs) of the wearable device, information enabling theuser device add funds to the wearable device, and/or the like. Asfurther shown in FIG. 1C, the user may utilize the wearable deviceapplication to select particular wearable device information and viewdetailed information associated with the particular wearable deviceinformation.

For example, as shown in FIG. 1D, assume that the user utilizes thewearable device application to select the information indicating theevent access privileges. In such an example, and as shown by referencenumber 150, when the user selects the information indicating the eventaccess privileges, the user device may provide, to the wearable device,information indicating access privileges for the wearable device at theevent. The user device may provide, for display to the user, theinformation indicating the access privileges for the wearable device atthe event. In some implementations, the information indicating theaccess privileges for the wearable device at the event may includeinformation indicating that the wearable device provides the user accessto venues A-C at the event, and that the wearable device does notprovide the user access to venues D-F at the event.

In some implementations, the wearable device application may enable theuser to configure the wearable device a variety of ways. For example, ifthe wearable device is utilized by a child at an amusement park, thewearable device may provide tracking information to a user device of aparent (e.g., via the wearable device application) so that the parentmay locate the child. In such an example, the tracking information maybe provided by the wireless component of the wearable device based on asignal being received at a location in the amusement park when thewearable device passes by the location. In another example, the parentmay utilize the wearable device application to control what may bepurchased with the wearable device by the child. In such an example, theparent may control food consumption of the child (e.g., so that thatchild cannot purchase junk food with the wearable device) by preventingthe wearable from being utilized to pay for particular foods.

As shown in FIG. 1E, now assume that the user utilizes the wearabledevice application to select the information enabling the user device toset up the lights of the wearable device. When the user selects theinformation enabling the user device to set up the lights of thewearable device, the user device may provide for display light settingsthat the user may specify. For example, the user may specify lightsettings associated with a color of the lights (e.g., Red), a patternfor the lights (e.g., a Z pattern), synchronization of the lights withmusic, and/or the like. As further shown in FIG. 1E, and by referencenumber 155, the user device may provide the light settings to thewearable device. In some implementations, the light settings may causethe wearable device to display a particular color (e.g., Red) ormultiple colors. Such implementations may enable the user to locatefriends at a crowded event without sufficient lighting. In someimplementations, the light settings may cause the wearable device todisplay a particular pattern (e.g., a Z pattern) or multiple patterns.Such implementations may enable the user to locate friends at a crowdedevent, may provide an indicator for a group of people at the event,and/or the like.

In some implementations, the light settings may cause the wearabledevice to synchronize a display of the lights with music being played atthe event (e.g., a concert, a music festival, and/or the like). In suchimplementations, the network receiver component of the wearable devicemay connect with a network that provides information associated with themusic being played at the event. The information associated with themusic being played may cause different lights of the wearable device tobe illuminated at different times. Such implementations may provide aunique and fun experience for the user at the event.

As shown in FIG. 1F, the user may purchase a soda, a hamburger, andFrench fries from a vendor at the event. As further shown, the vendormay be associated with a point of sale (PoS) device, and there may be nonetwork communication at the event. Thus, the sale of the soda, thehamburger, and the French fries to the user may be an offlinetransaction. The user may utilize the wearable device to pay for thesoda, the hamburger, and the French fries. As further shown in FIG. 1F,and by reference number 155, the PoS device may provide a charge (e.g.,$20) for the soda, the hamburger, and the French fries to the wearabledevice, and the NFC component of the wearable device may receive thecharge.

In some implementations, the receipt of the charge by the NFC componentof the wearable device may cause the security element of the wearabledevice to generate a secure token as payment for the charge. As furthershown in FIG. 1F, and by reference number 160, the wearable device mayprovide the secure token to the PoS device as payment for the charge. Insome implementations, the secure token may include informationidentifying the account (e.g., xxxx-xxxx) associated with the wearabledevice and an amount to charge the account (e.g., $20). In someimplementations, the PoS device may receive the secure token, but may beunable to redeem the token and receive payment since there is no networkcommunication at the event. However, the PoS device may store the securetoken, and may utilize the secure token to receive payment at a latertime when the PoS device is connected to a network.

As further shown in FIG. 1F, and by reference number 165, the wearabledevice may provide, to the user device, information indicating that thesecure token was provided to the PoS device. The user device may receivethe information, and may deduct the amount paid (e.g., $20) by thewearable device from the funds allocated to the wearable device. Forexample, if the wearable had $40 allocated to it prior to the purchase,the user device may deduct the $20 from the $40 to arrive at a balanceof $20 remaining on the wearable device. As further shown in FIG. 1F,the user device may provide, for display to the user, informationindicating that $20 was charged to the wearable device, and that abalance of $20 remains on the wearable device. The user device may alsodisplay to the user information requesting whether the user wishes toallocate more funds to the wearable device. In some implementations, theuser may wish to allocate more funds to the wearable device, and mayindicate this desire via the user device.

As shown in FIG. 1G, based on the desire of the user to allocate morefunds to the wearable device, the user device may provide, for displayto the user, information requesting an amount of funds to allocate tothe wearable device. In some implementations, the user may indicate thatthe user wishes to allocate a particular amount (e.g., $120) to thewearable device, and the user device may update the balance on thewearable device (e.g., to $140) based the user allocating the $120 tothe wearable device. As further shown in FIG. 1G, and by referencenumber 170, the user device may provide, to the wearable device,information indicating that the wearable device has $140 available forpurchases at the event. The wearable device may receive the informationindicating that the wearable device has $140 available for purchases atthe event. In some implementations, the user device may be unable toconnect with the account associated with the wearable device andallocate the $120 since there is no network communication at the event.However, the user device may store information indicating that $120 wasallocated to the wearable device, and may utilize such information towithdraw the $120 from the account at a later time when the user deviceis connected to a network.

As shown in FIG. 1H, assume that communication with a network isrestored at a later time, and that the user device and the PoS devicemay communicate with the network. In some implementations, and based onthe communication with the network, the PoS device may be able toreconcile the purchase (e.g., $20) with the event platform, and the userdevice may be able to reconcile the allocation of funds (e.g., $120), tothe wearable device, with the event platform. As further shown in FIG.1H, and by reference number 175, the user device may provide, to theevent platform, information indicating that $120 from the account wasallocated to the wearable device. As further shown in FIG. 1H, and byreference number 180, the PoS device may provide, to the event platform,the secure token indicating that $20 from the account was used topurchase the soda, the hamburger, and the French fries.

In some implementations, the event platform may receive the informationindicating that $120 from the account was allocated to the wearabledevice, and the secure token, and may deduct $140 from the account. The$140 deduction from the account may leave $160 in the account (e.g.,$300-$140). As further shown in FIG. 1G, and by reference number 185,the event platform may provide payment (e.g., $20) from the account tothe PoS device. The PoS device may receive the payment.

As shown in FIG. 1I, and by reference number 190, the user may utilizethe wearable device to access a building associated with an entity(e.g., a company, a government agency, an academic institution, and/orthe like). In some implementations, the wearable device may providecredentials associated with the user, and the credentials may beutilized to enable the user to access the building. In someimplementations, the user may utilize the wearable device to access aportion of a building (e.g., a laboratory of a building, a research anddevelopment portion of a building, and/or the like). As further shown inFIG. 1I, the user may utilize the wearable device to pay for a purchaseof a product and/or a service provided by the entity. For example, theuser may utilize the wearable device to purchase food, to purchasebooks, and/or the like.

As further shown in FIG. 1I, and by reference number 195, the eventplatform may provide information associated with an alert to the user,via the wearable device. In some implementations, the alert may beassociated with the entity, and may include an alert about a securitybreach associated with the entity, an alert about an emergency situation(e.g., a weather emergency, a fire emergency, a crime, and/or the like),an alert about a celebration (e.g., an employee's birthday, a studentand teacher function, and/or the like), and/or the like. The wearabledevice may receive the information associated with the alert, and maydisplay the information associated with the alert via visual and/ortactile feedback.

The implementations described in connection with FIG. 1I may be providedby the same wearable device and may eliminate a need for havingdifferent mechanisms for security purposes, for payment purposes, andfor alerts associated with the entity. In the implementations describedin connection with FIG. 1I, the wearable device may communicate with anetwork, and may be associated with the user device for securitypurposes (e.g., to provide secondary authentication for accessing abuilding).

In this way, several different stages of a transaction process areautomated and performed in an offline manner, which may remove wastefrom the process and may improve speed and efficiency of the process andconserve computing resources (e.g., processors, memory, and/or the likeassociated with attempting to continuously connect to a network).Furthermore, implementations described herein use a wearable device toperform tasks or roles that were not previously performed or werepreviously performed using human input. For example, the wearable deviceenables checking a balance available for the wearable device, addingfunds to the wearable device, and performing offline transactions withthe wearable device. Finally, the wearable enables conservation ofcomputing resources (e.g., processors, memory, and/or the like) thatwould otherwise be wasted in attempting to continuously connect to anetwork.

As indicated above, FIGS. 1A-1I are provided merely as examples. Otherexamples are possible and may differ from what was described with regardto FIGS. 1A-1I.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a user device 210, an event platform 220,a network 230, a PoS device 240, and a wearable device 250. Devices ofenvironment 200 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

User device 210 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information, such asinformation described herein. For example, user device 210 may include amobile phone (e.g., a smart phone, a radiotelephone, etc.), a laptopcomputer, a tablet computer, a handheld computer, a gaming device, awearable communication device (e.g., a smart wristwatch, a pair of smarteyeglasses, etc.), or a similar type of device. In some implementations,user device 210 may receive information from and/or transmit informationto event platform 220, PoS device 240, and/or wearable device 250.

Event platform 220 includes one or more devices that provide a wearabledevice application to user device 210 and that enables wearable device250 to access an event, pay for offline transactions at the event, andprovide a visual light display. In some implementations, event platform220 may be designed to be modular such that certain software componentsmay be swapped in or out depending on a particular need. As such, eventplatform 220 may be easily and/or quickly reconfigured for differentuses. In some implementations, event platform 220 may receiveinformation from and/or transmit information to one or more user devices210, PoS devices 240, and/or wearable devices 250.

In some implementations, as shown, event platform 220 may be hosted in acloud computing environment 222. Notably, while implementationsdescribed herein describe event platform 220 as being hosted in cloudcomputing environment 222, in some implementations, event platform 220may not be cloud-based (i.e., may be implemented outside of a cloudcomputing environment) or may be partially cloud-based.

Cloud computing environment 222 includes an environment that hosts eventplatform 220. Cloud computing environment 222 may provide computation,software, data access, storage, etc. services that do not requireend-user knowledge of a physical location and configuration of system(s)and/or device(s) that hosts event platform 220. As shown, cloudcomputing environment 222 may include a group of computing resources 224(referred to collectively as “computing resources 224” and individuallyas “computing resource 224”).

Computing resource 224 includes one or more personal computers,workstation computers, server devices, or other types of computationand/or communication devices. In some implementations, computingresource 224 may host event platform 220. The cloud resources mayinclude compute instances executing in computing resource 224, storagedevices provided in computing resource 224, data transfer devicesprovided by computing resource 224, etc. In some implementations,computing resource 224 may communicate with other computing resources224 via wired connections, wireless connections, or a combination ofwired and wireless connections.

As further shown in FIG. 2, computing resource 224 includes a group ofcloud resources, such as one or more applications (“APPs”) 224-1, one ormore virtual machines (“VMs”) 224-2, virtualized storage (“VSs”) 224-3,one or more hypervisors (“HYPs”) 224-4, and/or the like.

Application 224-1 includes one or more software applications that may beprovided to or accessed by user device 210, PoS device 240, and/orwearable device 250. Application 224-1 may eliminate a need to installand execute the software applications on user device 210, PoS device240, and/or wearable device 250. For example, application 224-1 mayinclude software associated with event platform 220 and/or any othersoftware capable of being provided via cloud computing environment 222.In some implementations, one application 224-1 may send/receiveinformation to/from one or more other applications 224-1, via virtualmachine 224-2.

Virtual machine 224-2 includes a software implementation of a machine(e.g., a computer) that executes programs like a physical machine.Virtual machine 224-2 may be either a system virtual machine or aprocess virtual machine, depending upon use and degree of correspondenceto any real machine by virtual machine 224-2. A system virtual machinemay provide a complete system platform that supports execution of acomplete operating system (“OS”). A process virtual machine may executea single program, and may support a single process. In someimplementations, virtual machine 224-2 may execute on behalf of a user(e.g., an operator of event platform 220), and may manage infrastructureof cloud computing environment 222, such as data management,synchronization, or long-duration data transfers.

Virtualized storage 224-3 includes one or more storage systems and/orone or more devices that use virtualization techniques within thestorage systems or devices of computing resource 224. In someimplementations, within the context of a storage system, types ofvirtualizations may include block virtualization and filevirtualization. Block virtualization may refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem may be accessed without regard to physical storage orheterogeneous structure. The separation may permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization may eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This may enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

Hypervisor 224-4 may provide hardware virtualization techniques thatallow multiple operating systems (e.g., “guest operating systems”) toexecute concurrently on a host computer, such as computing resource 224.Hypervisor 224-4 may present a virtual operating platform to the guestoperating systems, and may manage the execution of the guest operatingsystems. Multiple instances of a variety of operating systems may sharevirtualized hardware resources.

Network 230 includes one or more wired and/or wireless networks. Forexample, network 230 may include a cellular network (e.g., a fifthgeneration (5G) network, a long-term evolution (LTE) network, a thirdgeneration (3G) network, a code division multiple access (CDMA) network,etc.), a public land mobile network (PLMN), a local area network (LAN),a wide area network (WAN), a metropolitan area network (MAN), atelephone network (e.g., the Public Switched Telephone Network (PSTN)),a private network, an ad hoc network, an intranet, the Internet, a fiberoptic-based network, and/or the like, and/or a combination of these orother types of networks.

PoS device 240 includes a device that conducts and completes atransaction at a time and place of the transaction. PoS device 240 maycalculate an amount owed by a customer, may indicate that amount, mayprepare an invoice for the customer, and may indicate options for thecustomer to make payment. PoS device 240 may be point at which acustomer makes a payment to a merchant in exchange for goods or afterprovision of a service. After receiving payment, PoS device 240 mayissue a printed or an electronic receipt for the transaction.

Wearable device 250 may include a device that is worn by a user,attached to an item of clothing of the user, attached to accessories ofthe user (e.g., a backpack), and/or the like. In some implementations,wearable device 250 may provide access to an event, may pay for offlinetransactions at the event, may provide a visual light display, and/orthe like. In some implementations, wearable device 250 may include aband to be worn around a wrist of a user and a housing connected to theband. Alternatively, the housing of wearable device 250 may be connectedto a mechanism other than the band, such as a lanyard, a connector forconnecting to a backpack or an article of clothing, and/or the like. Thehousing may support multiple LEDs, and may house a NFC component,security element, a wireless component, and a network receivercomponent.

Each LED may include a two-lead semiconductor light source, such as ap-n junction diode that emits light when activated. In someimplementations, each LED may emit a particular color or a plurality ofdifferent colors. In some implementations, when a suitable voltage isapplied to the leads of each LED, electrons may recombine with electronholes within each LED, releasing energy in the form of photons. Thiseffect is called electroluminescence, and a color of light maycorresponding to an energy of the photon, and may be determined by anenergy band gap of the semiconductor.

NFC component may include a component supporting communication protocolsthat enable wearable device 250 and another device (e.g., user device210, PoS device 240, and/or the like) to establish communication bybringing wearable device 250 and other device within a particulardistance of each other. In some implementations, the NFC component mayenable wearable device 250 to be used with contactless payment systems(e.g., PoS device 240) so that wearable device 250 can performtransactions (e.g., make contactless payments).

The security element may include a component that generates a securetoken (e.g., a one-time password (OTP) token) when wearable device 250is utilize to perform transactions (e.g., make contactless payments). Insome implementations, the secure token may provide authentication forthe user when the user accesses the funds on wearable device 250,accesses accounts associated with the user (e.g., bank accounts, creditcard accounts, debit card accounts, and/or the like), and/or the like.In some implementations, when the NFC component is energized by acontactless payment system (e.g., when wearable device 250 is being usedto conduct a transaction for a particular amount of funds), the NFCcomponent being energized may cause the security element toautomatically generate a secure token for the particular amount offunds. The security element may provide the secure token to thecontactless payment system via the NFC component.

The wireless component may include component that supports a particularwireless technology standard (e.g., Bluetooth, Zignee, WiFi, and/or thelike), and enables wearable device 250 to communicate wirelessly withother devices (e.g., user device 210) over short distances. In someimplementations, the wireless component may enable wearable device 250to communicate with user device 210 so that user device 210 may displayinformation associated with wearable device 250 (e.g., a ticket numberidentifier, an amount of available funds, event access privileges,and/or the like).

The network receiver component may include a component supportingnetwork communication protocols (e.g., wide area network (WAN)protocols, cellular network protocols, and/or the like) that enablewearable device 250 to connect to a network, perform onlinetransactions, and/or the like. In some implementations, the networkreceiver component may enable wearable device 250 to connect with anetwork and receive event information (e.g., music information, soundinformation, and/or the like), information to configure the LEDs,information to synchronize the LEDs with the event information, and/orthe like.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to user device 210, event platform 220, computingresource 224, PoS device 240, and/or wearable device 250. In someimplementations, user device 210, event platform 220, computing resource224, PoS device 240, and/or wearable device 250 may include one or moredevices 300 and/or one or more components of device 300. As shown inFIG. 3, device 300 may include a bus 310, a processor 320, a memory 330,a storage component 340, an input component 350, an output component360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for utilizing awearable device to access an event, pay for offline transactions at theevent, and provide a visual light display. In some implementations, oneor more process blocks of FIG. 4 may be performed by wearable device250. In some implementations, one or more process blocks of FIG. 4 maybe performed by another device or a group of devices separate from orincluding wearable device 250, such as user device 210, event platform220, and/or PoS device 240.

As shown in FIG. 4, process 400 may include receiving and storing ticketinformation and information indicating a quantity of funds allocatedfrom an account associated with a user (block 410). For example,wearable device 250 may receive and store ticket information andinformation indicating a quantity of funds allocated from an accountassociated with a user. In some implementations, user device 210 mayprovide, to event platform 220, a request for a ticket and an account toutilize for purchasing the ticket. In some implementations, user device210 may provide, to event platform 220, a request to add funds to theticket. In some implementations, event platform 220 may charge theaccount for the ticket, and may generate a ticket number based on therequest for the ticket and the account to utilize for purchasing theticket. Event platform 220 may charge the amount of funds to the account(e.g., associated with a user of user device 210), and may add the fundsto the ticket. In some implementations, the ticket may be in the form ofwearable device 250.

In some implementations, event platform 220 may provide, to wearabledevice 250, information indicating the ticket number and the amount offunds allocated to wearable device 250 from the account. In suchimplementations, wearable device 250 may receive the informationindicating the ticket number and the amount of funds allocated towearable device 250 from the account, and may store the informationindicating the ticket number and the amount of funds allocated towearable device 250 from the account. In some implementations, wearabledevice 250 may receive other information from event platform 220 (e.g.,information associated with the event, information indicating accessprivileges for the event, information indicating light settings for thewearable device, and/or the like), and may store the other information.

As further shown in FIG. 4, process 400 may include pairing with a userdevice associated with the user based on a request to pair received fromthe user device (block 420). For example, wearable device 250 may pairwith user device 210 associated with the user based on a request to pairreceived from user device 210. In some implementations, user device 210may execute a wearable device application, and the wearable deviceapplication may provide a user interface that inquires whether the userwants to pair user device 210 with wearable device 250. In someimplementations, if the user wants to pair user device 210 with wearabledevice 250, the wearable device application may cause user device 250 toprovide, to wearable device 250, a signal requesting pairing withwearable device 250. In some implementations, the wireless component ofwearable device 250 may receive the signal requesting the pairing. Insome implementations, wearable device 250 may automatically accept thepairing with user device 210 and may provide a signal, indicating thatthe pairing is accepted, to user device 210. In such implementations,user device 210 and wearable device 250 may be paired and maycommunicate with each other. In some implementations, wearable device250 may require provision of the ticket information or some otherverification before pairing with user device 210.

As further shown in FIG. 4, process 400 may include providing, to theuser device and via the pairing, wearable device information (block430). For example, wearable device 250 may provide, to user device 210and via the pairing, wearable device information. In someimplementations, once wearable device 250 and user device 210 arepaired, wearable device 250 may automatically provide the wearabledevice information to user device 210. User device 210 may receive thewearable device information, and may provide the wearable deviceinformation for display to the user. In some implementations, thewearable device information may include the ticket number associatedwith wearable device 250, an amount of funds allocated to wearabledevice 250, information indicating event access privileges, informationenabling user device 210 to set up the lights (e.g., the LEDs) ofwearable device 250, information enabling user device 210 add funds towearable device 250, and/or the like. In some implementations, the usermay utilize the wearable device application to select particularwearable device information and view detailed information associatedwith the particular wearable device information.

For example, if the user utilizes the wearable device application toselect the information indicating the event access privileges, userdevice 210 may provide, to wearable device 510, information indicatingaccess privileges for wearable device 250, and hence the user, at theevent. User device 210 may provide, for display to the user, theinformation indicating the access privileges for wearable device 250 atthe event.

As further shown in FIG. 4, process 400 may include receiving andimplementing light settings provided by the user device via the pairing(block 440). For example, wearable device 250 may receive and implementlight settings provided by user device 210 via the pairing. In someimplementations, if the user selects the information enabling userdevice 210 to set up the lights of wearable device 250, user device 210may provide for display light settings that the user may specify. Forexample, the user may specify light settings associated with a color ofthe lights, a pattern for the lights, synchronization of the lights withmusic, and/or the like. In some implementations, user device 210 mayprovide the light settings to wearable device 250, and wearable device250 may receive and implement the light settings. In someimplementations, the light settings may cause wearable device 250 todisplay a particular color or multiple different colors. In someimplementations, the light settings may cause wearable device 250 todisplay a particular pattern, multiple different patterns, an image,multiple different images, and/or the like.

In some implementations, the light settings may cause wearable device250 to synchronize a display of the lights of wearable device 250 withsound (e.g., music, a video, a speech, and/or the like) being played atthe event (e.g., a concert, a music festival, and/or the like). In suchimplementations, the network receiver component of wearable device 250may connect with a network that provides information associated with thesound being played at the event. The information associated with thesound being played at the event may cause different lights of wearabledevice 250 to be illuminated at different times. In someimplementations, the information associated with the sound being playedmay cause the lights of wearable device 250 to provide a displayresembling an equalizer.

As further shown in FIG. 4, process 400 may include generating a tokenfor a point of sale device for a charge incurred during an offlinetransaction with the point of sale device (block 450). For example,wearable device 250 may generating a token for PoS device 240 for acharge incurred during an offline transaction with PoS device 240. Insome implementations, the user may perform an offline transaction (e.g.,make a purchase) with PoS device 240 at the event. The user may utilizewearable device 250 to pay for the purchase, and PoS device 240 mayprovide a charge for the purchase to wearable device 250. In someimplementations, the NFC component of wearable device 250 may receivethe charge from PoS device 240. In some implementations, the receipt ofthe charge by the NFC component of wearable device 250 may cause thesecurity element of wearable device 250 to automatically generate asecure token as payment for the charge. In some implementations, thereceipt of the charge from PoS device 240 may cause the NFC component ofwearable device 250 to become energized, and the energizing of the NFCcomponent may cause the security element of wearable device 250 toautomatically generate the secure token.

As further shown in FIG. 4, process 400 may include providing the tokento the point of sale device and providing, to the user device,information indicating provision of token (block 460). For example,wearable device 250 may provide the token to PoS device 240 and mayprovide, to user device 210, information indicating provision of tokento PoS device 240. In some implementations, wearable device 250 mayprovide a secure token to PoS device 240 as payment for the charge. Insome implementations, the secure token may include informationidentifying the account associated with wearable device 250 and anamount to charge the account. In some implementations, PoS device 240may receive the secure token, but may be unable to redeem the token andreceive payment since there is no network communication at the event.However, PoS device 240 may store the secure token, and may utilize thesecure token to receive payment at a later time when PoS device 240 isconnected to a network.

In some implementations, wearable device 250 may provide, to user device210, information indicating that the secure token was provided to PoSdevice 240. In some implementations, user device 210 may receive theinformation indicating that the secure token was provided to PoS device240, and may deduct the amount paid by wearable device 250 from thefunds allocated to wearable device 250.

As further shown in FIG. 4, process 400 may include receiving, from theuser device, information indicating that an additional quantity of fundswere allocated from the account (block 470). For example, wearabledevice 250 may receive, from user device 210, information indicatingthat an additional quantity of funds were allocated from the account ofthe user to wearable device 250. In some implementations, user device210 may provide, for display to the user, information requesting whetherthe user wishes to allocate more funds to wearable device 250. In someimplementations, the user may wish to allocate more funds to wearabledevice 250, and may indicate this desire via user device 210.

In some implementations, based on the desire of the user to allocatemore funds to wearable device 250, user device 210 may provide, fordisplay to the user, information requesting an amount of funds toallocate to wearable device 250. In some implementations, the user mayindicate that the user wishes to allocate a particular amount towearable device 250, and user device 210 may update the balance onwearable device 250 based the user allocating the particular amount towearable device 250. In some implementations, user device 210 mayprovide, to wearable device 250, information indicating that wearabledevice 250 has an updated balance of funds available for purchases atthe event. In some implementations, wearable device 250 may receive theinformation indicating that the wearable device has an updated balance(e.g., with an additional quantity of funds) available for purchases atthe event. In some implementations, user device 210 may be unable toconnect with the account associated with wearable device 250 andallocate the particular amount since there is no network communicationat the event. However, in such implementations, user device 210 maystore information indicating that the particular amount was allocated towearable device 250, and may utilize such information to withdraw theparticular amount from the account at a later time when user device 210is connected to a network.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

Some implementations described herein include a wearable device thatprovides access to an event, pays for offline transactions at the event,and provides a visual light display. The wearable device may include awireless component, a NFC component, a security element, a networkreceiver component, and multiple LEDs. The wireless component may enablethe wearable device to connect to a user device (e.g., a mobile phone)so that a user of the wearable device may check a balance of fundsavailable to the wearable device and may add to the balance of funds.The NFC component and the security element may enable the wearabledevice to be used to pay for offline transactions at the event. Thenetwork receiver component and the multiple LEDs may enable the wearabledevice to provide a variety of light displays that may be synchronizedto sounds (e.g., music) associated with the event.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, or the like.A user interface may provide information for display. In someimplementations, a user may interact with the information, such as byproviding input via an input component of a device that provides theuser interface for display. In some implementations, a user interfacemay be configurable by a device and/or a user (e.g., a user may changethe size of the user interface, information provided via the userinterface, a position of information provided via the user interface,etc.). Additionally, or alternatively, a user interface may bepre-configured to a standard configuration, a specific configurationbased on a type of device on which the user interface is displayed,and/or a set of configurations based on capabilities and/orspecifications associated with a device on which the user interface isdisplayed.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwaremay be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a device andfrom a user device, a request for a ticket associated with an event andinformation indicating a payment account to utilize for purchasing theticket, the ticket being associated with a wearable device; applying, bythe device, a charge to the payment account to utilize for purchasingthe ticket; generating, by the device, ticket information based on therequest for the ticket and the payment account to utilize for purchasingthe ticket; receiving, by the device, a request for a wearable deviceapplication to enable the user device to communicate with the wearabledevice, the wearable device application enabling the user device toconfigure the wearable device; comparing, by the device, the ticketinformation and the request to determine whether the request for thewearable device application is legitimate; and selectively providing, bythe device, the wearable device application to the user device, thewearable device application being provided when it is determined thatthe request for the wearable device application is legitimate, and thewearable device application not being provided when it is determinedthat the request for the wearable device application is not legitimate.2. The method of claim 1, further comprising: receiving informationindicating that a quantity of funds was allocated to the wearabledevice; and deducting the quantity of funds from the payment account. 3.The method of claim 1, wherein the event includes one of: a concert, afestival, an event at a university, a sporting event, an event at atheme park, or a trade show.
 4. The method of claim 1, furthercomprising: receiving, from a point of sale device, a token indicatingthat a quantity of funds was used to purchase one or more items; anddeducting the quantity of funds from the payment account.
 5. The methodof claim 4, wherein the token is generated during an offline transactionwith the point of sale device, and further comprising: providing paymentto the point of sale device from the payment account to the point ofsale device, the point of sale device to utilize the token to receivepayment for the one or more items from the payment account, at a latertime and via an online transaction.
 6. The method of claim 1, furthercomprising: providing information associated with an alert to thewearable device, the information associated with the alert to bedisplayed by the wearable device via one or more of: tactile feedback;or visual feedback.
 7. The method of claim 6, wherein the alert isassociated with at least one of: an emergency situation; a securitybreach; or a celebration.
 8. A device for wireless communication,comprising: a memory; and one or more processors operatively coupled tothe memory, the memory and the one or more processors configured to:receive, from a user device, a request for a ticket associated with anevent and information indicating a payment account to utilize forpurchasing the ticket, the ticket being associated with a wearabledevice; generate ticket information based on the request for the ticketand the payment account to utilize for purchasing the ticket; receive arequest for a wearable device application to enable the user device tocommunicate with the wearable device; compare the ticket information andthe request to determine whether the request for the wearable deviceapplication is legitimate; and selectively provide the wearable deviceapplication to the user device, the wearable device application beingprovided when it is determined that the request for the wearable deviceapplication is legitimate, and the wearable device application not beingprovided when it is determined that the request for the wearable deviceapplication is not legitimate.
 9. The device of claim 8, wherein thewearable device application enables the user device to configure thewearable device.
 10. The device of claim 8, wherein the event includesone of: a concert, a festival, an event at a university, a sportingevent, an event at a theme park, or a trade show.
 11. The device ofclaim 8, wherein the one or more processors are further configured to:receive, from a point of sale device, a token indicating that a quantityof funds was used to purchase one or more items; and deduct the quantityof funds from the payment account.
 12. The device of claim 11, whereinthe one or more processors, when determining whether the request for thewearable device application is legitimate, are further configured to:compare the ticket information to user credentials associated with theuser device.
 13. The device of claim 8, wherein the one or moreprocessors are further configured to: provide information associatedwith an alert to the wearable device.
 14. The device of claim 13,wherein the alert is associated with a security breach associated withthe event.
 15. A non-transitory computer-readable medium storing one ormore instructions for wireless communication, the one or moreinstructions comprising: one or more instructions that, when executed byone or more processors of a device, cause the one or more processors to:receive, from a user device, a request for a ticket associated with anevent and information indicating a payment account to utilize forpurchasing the ticket, the ticket being associated with a wearabledevice; generate ticket information based on the request for the ticketand the payment account to utilize for purchasing the ticket; receive arequest for a wearable device application to enable the user device tocommunicate with the wearable device, the wearable device applicationenabling the user device to configure the wearable device; determinewhether the request for the wearable device application is legitimate;and selectively provide the wearable device application to the userdevice, the wearable device application being provided when it isdetermined that the request for the wearable device application islegitimate, and the wearable device application not being provided whenit is determined that the request for the wearable device application isnot legitimate.
 16. The non-transitory computer-readable medium of claim15, wherein the one or more instructions, when executed by the one ormore processors, further cause the one or more processors to: receiveinformation indicating that a quantity of funds was allocated to thewearable device; and deduct the quantity of funds from the paymentaccount.
 17. The non-transitory computer-readable medium of claim 15,wherein the event includes one of: a concert, a festival, an event at auniversity, a sporting event, an event at a theme park, or a trade show.18. The non-transitory computer-readable medium of claim 15, wherein theone or more instructions, when executed by the one or more processors,further cause the one or more processors to: receive, from a point ofsale device, a token indicating that a quantity of funds was used topurchase one or more items; and deduct the quantity of funds from thepayment account.
 19. The non-transitory computer-readable medium ofclaim 15, wherein the one or more instructions, when executed by the oneor more processors, further cause the one or more processors to: provideinformation associated with an alert to the wearable device.
 20. Thenon-transitory computer-readable medium of claim 19, wherein theinformation associated with the alert is to be displayed by the wearabledevice via one or more of: tactile feedback, or visual feedback.